Sets the audit level for changes made to the redundancy definition. When set to 0, auditing is off. See Service Audit Levels for more information about this keyword.

REDUNDANT indicates whether Redundancy is enabled for this service and it is part of a redundant set with other services.

• Set to TRUE to enable Redundancy for this service and indicate that it is in a redundant relationship with another service within the redundancy environment.
• Set to FALSE or commented out to disable Redundancy for this service.

See Redundancy for more configuration details. A redundancy definition for your CygNet environment is configured in the CygNet Redundancy Editor.

The IN_REDUNDANT_SET (Service in redundant set) info item will report whether this service is part of a redundant relationship.

REPL_CHECK_INTERVAL indicates the interval (in seconds) to check before performing the next replication synchronization. This value determines the replication synchronization frequency.

After performing a sync, a replicating service will subtract the amount of time the sync took from the check interval time to determine how long to wait until the next sync. For example, if the check interval is 60 seconds and the sync takes 40 seconds, the service will only wait 20 seconds before starting the next sync. If the whole sync time exceeds the frequency, then the replicating service will wait for half the sync interval (30 seconds in this case) before starting the next sync.

The REPL_CHECK_INTERVAL (Repl Poll Secs) info item will report the interval that a replicated service will check the source change queue for new updates. If the service is not replicating REPL_CHECK_INTERVAL will respond with an empty string.

REPL_DELAY_MAX indicates the number of seconds a service is allowed to be behind in replication before it is considered to be behind. If this keyword is disabled, the value defaults to double the REPL_CHECK_INTERVAL time. Best practice recommends enabling and setting a meaningful value for REPL_DELAY_MAX for all replicating services. A recommended value would be a longer time interval than you would expect any sync interval to take.

The REPL_DELAY_MAX (Allowed repl delay) info item will report the time elapsed since the service was last fully in sync. Time is calculated as the delta between "now" and the end of the last full sync that has completed. If the time since the last successful sync exceeds the REPL_DELAY_MAX value, and the REPL_INT_VAL_STATE (Int repl val state) info item is currently "Normal", then the REPL_INT_VAL_STATE info item is set to "Delayed." The state can only be set back to "Normal" when the time between two syncs is less than the REPL_DELAY_MAX time.

Specifies the number of seconds to delay the startup of the ARS, so that the service can synchronize with other ARS services on the same domain. Setting this keyword may prevent multiple services starting up and running on the same domain for a short time after a hard failover.

For services in a redundant environment we recommend you start with a value of 30, then consider adjusting as needed. For non-redundant services, we recommend you leave the value at zero.

An optional keyword that specifies up to ten additional domains on which this ARS can run.

Allowing an ARS to run on several domains will reduce the overhead of managing multiple RSM and ARS services in a complex redundant environment. Service shutdown and startup delay time will be reduced, as the last ARS in a failover event will continue to run after a local or data-center failover has occurred. Other systemic benefits include improved management by a single ARS in a failover set of the CAL, host activation, and other license-master-controlled entities (CvsMetadata, license master, CygNet time zones). The ADDITIONAL_DOMAINS keyword is not required if you’re using CygNet Redundancy and the ARS is marked as REDUNDANT in its config file.

Additionally, you can specify a Domain when configuring the AUD service keyword in the ARS service configuration file. For a redundant environment, if the Audit service configured in the Ars.cfg file does not specify a Domain, any AUD services of that name on all Domains within the redundancy definition will receive audit entries from that ARS because the ARS is not a unique identity. By specifying a Domain for the AUD in the Ars.cfg file you can limit the sending of audit entries to just that individual service. Note that replicating AUD services won't accept entries from sources other than the replicated AUD. If a Domain is specified for the AUD keyword, and an ARS sends entries to a replicating AUD service, no error messages will be reported in the AUD or ELS log files, unlike other services.

The Site and Service name of the service’s AUD, in Site.Service format.